Installing and Managing FTP 7
Microsoft
has provided an updated version of FTP services for use with Windows
Server 2008. To enable FTP 7, you must manually download and install
the Microsoft FTP Publishing Service for IIS 7.0. You can obtain the
necessary files and installation instructions by accessing the
Downloads section of the Microsoft Internet Information Services (IIS)
Web site at http://www.iis.net/downloads/.
Avoid running both FTP 6 and FTP 7 on the same computer at the same
time because this might cause conflicts with site and port
configurations. To avoid these problems, remove FTP 6 from the computer
prior to installing FTP 7, as described earlier in this lesson.
The
primary administration tool for FTP 7 is IIS Manager. Systems
administrators can use IIS Manager to configure both HTTP and FTP
services, using the same administrative interface. Once you have downloaded and installed FTP 7, you can launch IIS Manager to configure server settings. Figure 12 shows the available FTP-related options for Default Web Site.
Managing FTP Sites
After
you have installed and configured FTP 7, you can use IIS Manager to
create and configure FTP sites. In this section, you will learn how to
create new FTP sites and how to add FTP functionality to an existing
Web site.
Creating a New FTP Site
You
can create new FTP sites to support different groups of users or to
provide access to different sets of files. To create a new FTP site,
right-click either the server object or the Sites folder in the left
pane of IIS Manager, and then select Add FTP Site. This will start the
Add FTP Site Wizard. The first page prompts you for information about
the name of the site. (See Figure 13.)
This name will be used for administration purposes, so you should
choose a descriptive name if you plan to host multiple FTP sites on the
same server. The Physical Path setting enables you to specify the root
folder for the FTP site. You can choose any existing folder path, but
many installations will use a subfolder within the %SystemDrive%\Inetpub folder.
On the second page of the process, you can specify the binding and SSL settings for the new FTP site. (See Figure 7-14.) The binding settings include the following options:
IP Address
The default setting is for the FTP site to respond to all incoming
requests on any network adapter or IP address on the server. If the
computer is configured with multiple network adapters or multiple IP
addresses on the same adapter, you can choose a specific address, using
the drop-down list.
Port
This is the TCP port on which the FTP site will respond. By convention,
the default port for FTP communications is port 21. If you choose a
different port, FTP users will be required to configure their FTP
client software to connect by using the server’s port number.
Virtual Host
Administrators can create multiple Web sites that respond on the same
IP address and port through virtual host names. These names rely on
Domain Name System (DNS) entries to determine to which site users will
connect. Users can also include the virtual host name as part of their
logon name to specify to which site they want to log on.
Start FTP Site Automatically When
this option is enabled, the FTP site will start automatically and
whenever the computer is rebooted or the FTP service is restarted. If
you plan to start the FTP site manually whenever it is required,
disable this option.
You
can also select an SSL Certificate and whether to allow or require
Secure Socket Layer (SSL) connections for this FTP site. You will learn
more about these options later in this section.
On the Authentication And Authorization Information page, you specify how security will be managed for the new FTP site. (See Figure 15.)
When
you click the Finish button, the new FTP site will be created and added
to the left pane of IIS Manager. When you select the FTP Site object,
you can use the commands in the Actions pane to start, restart, or stop
the FTP site. You will also see a list of all the configuration options
for the FTP site in the center pane of IIS Manager. (See Figure 16.)
